chore: standardize repository config by afc163 · Pull Request #165 · react-component/switch

afc163 · 2026-06-26T09:06:22Z

Summary

Standardize this rc-component repository as part of the Ant Design rc-component maintenance sweep.

Tracking issue: ant-design/ant-design#58514

Scope

Redesign README.md and README.zh-CN.md with centered title, Ant Design ecosystem branding, aligned badges, scoped Bundlephobia badge, install command, Usage, Development, Release, and License sections.
Standardize package metadata, GitHub repo metadata, npm package name, package entry fields, types: "./es/index.d.ts", publishConfig, and release flow through @rc-component/np.
Align shared dependencies and scripts for React, testing-library, Jest/Vitest where existing, TypeScript, ESLint, Prettier, Less, dumi, father, Husky, lint-staged, and Dependabot.
Use the shared react-component/rc-test/.github/workflows/test-utoo.yml@main workflow, React Doctor, Codecov, CodeQL, updated GitHub Actions versions, and guarded Surge preview fallback.
Keep Vercel preview configuration compatible with docs-dist output and remove legacy now-build / Cloudflare Pages residue.
Keep API docs, demos, tests, TypeScript checks, funding metadata, and npm package files aligned with the repository standardization matrix.

Notes

No breaking runtime behavior is intended.
React peer dependency ranges are preserved when narrowing them would be a breaking change.
secrets: inherit is kept until react-component/rc-test#176 is merged, then it can be narrowed to explicit CODECOV_TOKEN forwarding.

vercel · 2026-06-26T09:06:29Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
switch	Ready	Preview, Comment	Jun 29, 2026 6:38am

coderabbitai · 2026-06-26T09:06:32Z

Warning

Review limit reached

@afc163, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable usage-based reviews in Billing to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information, and refer to the rate limits docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3813258f-7f0d-4553-93b2-78142f8a6959

📥 Commits

Reviewing files that changed from the base of the PR and between 149568c and e17e09b.

📒 Files selected for processing (18)

.dumirc.ts
.eslintignore
.github/FUNDING.yml
.github/dependabot.yml
.github/workflows/main.yml
.github/workflows/react-component-ci.yml
.github/workflows/react-doctor.yml
.github/workflows/surge-preview.yml
.gitignore
.husky/pre-commit
.prettierignore
LICENSE
README.md
README.zh-CN.md
docs/index.md
package.json
tsconfig.json
vercel.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch codex/standardize-rc-config

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-06-26T09:06:35Z

❌ Deploy failed

	❌ Failed
	🔗 Preview ~~https://react-component-switch-preview-pr-165.surge.sh~~ _{(may be unavailable)}
	📝 Commit	`e17e09b`
	🪵 Logs	View logs

📋 Build log (last lines)

npm warn exec The following package was not found and will be installed: surge@0.27.4

   Running as afc163@gmail.com (Student)

        project: ./docs-dist
         domain: react-component-switch-preview-pr-165.surge.sh
           size: 27 files, 1.5 MB

   Aborted - you do not have permission to publish to react-component-switch-preview-pr-165.surge.sh

_{🤖 Powered by surge-preview}

socket-security · 2026-06-26T09:06:57Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Potential typosquat: npm `slash2` as a typo of slash Did you mean: slash2 From: `?` → `npm/rc-test@7.1.3` → `npm/slash2@2.0.0` ℹ Read more on: This package \| This alert \| What is a typosquat? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/slash2@2.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `css-tree` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@umijs/fabric@4.0.1` → `npm/css-tree@3.2.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/css-tree@3.2.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `cssom` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/rc-test@7.1.3` → `npm/cssom@0.3.8` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cssom@0.3.8`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `cssom` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/rc-test@7.1.3` → `npm/cssom@0.5.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cssom@0.5.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `eslint-plugin-react` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@umijs/fabric@4.0.1` → `npm/eslint-plugin-react@7.37.5` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/eslint-plugin-react@7.37.5`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `eslint-plugin-unicorn` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/eslint-plugin-unicorn@56.0.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/eslint-plugin-unicorn@56.0.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

gemini-code-assist

Code Review

This pull request updates the project's configuration, documentation, and build scripts, including transitioning to dumi and rc-test, adding Vercel deployment configurations, and updating the README. Feedback is provided regarding the removal of strict type-checking in tsconfig.json which reduces type safety, and the removal of the prepare script in package.json which prevents automatic Husky git hooks installation.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

codecov · 2026-06-26T09:07:46Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (552d320) to head (e17e09b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #165   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           34        32    -2     
  Branches         9         8    -1     
=========================================
- Hits            34        32    -2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

vercel · 2026-06-26T18:16:04Z

Deployment failed with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/afc163s-projects?upgradeToPro=build-rate-limit

socket-security · 2026-06-27T17:31:23Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/husky@9.1.7
	npm/rc-test@7.1.3
	npm/@types/react-dom@18.3.7
	npm/@types/react@19.2.17 ⏵ 18.3.31			⁺¹
	npm/cross-env@10.1.0
	npm/@umijs/fabric@4.0.1
	npm/@testing-library/react@15.0.7
	npm/eslint-plugin-unicorn@56.0.1
	npm/typescript@5.9.3
	npm/lint-staged@16.4.0

View full report

chore: standardize repository config

3a083d4

gemini-code-assist Bot reviewed Jun 26, 2026

View reviewed changes

Comment thread tsconfig.json

Comment thread package.json

fix: keep default CodeQL setup

58b06b5

vercel Bot deployed to Preview June 26, 2026 09:15 View deployment

afc163 mentioned this pull request Jun 26, 2026

Track rc component repository standardization ant-design/ant-design#58514

Closed

chore: address AI review feedback

b70ce21

vercel Bot deployed to Preview June 26, 2026 17:42 View deployment

afc163 added 2 commits June 27, 2026 01:56

docs: standardize README release details

8274bc5

ci: make surge preview non-blocking

42387a0

vercel Bot deployed to Preview June 26, 2026 18:14 View deployment

afc163 added 2 commits June 27, 2026 02:25

ci: keep surge preview as fallback

547844f

docs: refine README usage and ecosystem note

6945552

vercel Bot deployed to Preview June 27, 2026 05:18 View deployment

afc163 added 3 commits June 27, 2026 13:22

ci: isolate surge preview token

e5291b5

chore: address review comments

e7e300e

docs: add Chinese README

2aa54df

vercel Bot deployed to Preview June 27, 2026 14:34 View deployment

afc163 added 3 commits June 27, 2026 22:35

docs: add Ant Design logo to README

356d8ff

docs: refine bilingual README branding

93b7216

chore: standardize rc tooling and docs

622b1c9

afc163 added 3 commits June 28, 2026 02:01

chore: address standardization review comments

a7f3292

chore: include father config in type checks

5e6923d

docs: add license file

44e511e

afc163 added 17 commits June 28, 2026 14:01

ci: use actions checkout v7

b645765

chore: standardize package metadata

74baec6

ci: standardize dependabot updates

bbec15f

chore: ignore generated docs artifacts

e6c8f2d

chore: refine preview workflow ignores

ead3aa2

docs: polish Chinese README wording

5def596

chore: align tooling ignores and typescript

53210b6

docs: polish Chinese README wording

8fe76a0

docs: document dumi dev server port

b26ebba

chore: standardize husky configuration

6b5435c

chore: standardize package type entry

3e1004a

docs: normalize readme badges

6e2d36f

ci: limit reusable workflow secrets

3b1b5c3

ci: restore reusable workflow compatibility

0ee74ca

docs: polish zh-CN readme wording

b9ae748

ci: narrow surge preview permissions

c068cb7

chore: limit reusable workflow secrets

e17e09b

vercel Bot deployed to Preview June 29, 2026 06:38 View deployment

afc163 merged commit 9ab8f18 into master Jun 29, 2026
15 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: standardize repository config#165

chore: standardize repository config#165
afc163 merged 33 commits into
masterfrom
codex/standardize-rc-config

afc163 commented Jun 26, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Jun 26, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Jun 26, 2026 •

edited

Loading

Review limit reached

Uh oh!

github-actions Bot commented Jun 26, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 26, 2026 •

edited

Loading

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

Uh oh!

Uh oh!

codecov Bot commented Jun 26, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Jun 26, 2026

Uh oh!

socket-security Bot commented Jun 27, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

afc163 commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Scope

Notes

Uh oh!

vercel Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

github-actions Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ Deploy failed

Uh oh!

socket-security Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

codecov Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

vercel Bot commented Jun 26, 2026

Uh oh!

socket-security Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

afc163 commented Jun 26, 2026 •

edited

Loading

vercel Bot commented Jun 26, 2026 •

edited

Loading

coderabbitai Bot commented Jun 26, 2026 •

edited

Loading

github-actions Bot commented Jun 26, 2026 •

edited

Loading

socket-security Bot commented Jun 26, 2026 •

edited

Loading

codecov Bot commented Jun 26, 2026 •

edited

Loading

socket-security Bot commented Jun 27, 2026 •

edited

Loading